Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 090 / update24.arc / PROLIX24.DOC next >

Wrap

Text File | 1986-05-09 | 79.1 KB | 1,631 lines

UpDate User's Manual UpDate v2.4 User's Manual ------------- System Requirements: IBM PC/XT/AT or IBM-compatible computer One or more hard-disk drives and(or) One or more floppy drives [Floppy-Only Systems require High-Capacity Drives] 80-column screen PC-DOS or MS-DOS, v2.0 or higher 192K RAM Copyright Holder hereby grants permission to copy and distribute UpDate programs freely, without any charge whatsoever, on condition that no changes are made in program content. Please report bugs/criticisms/suggestions to Copyright Holder. UP.EXE compiled 9 May 1986 Copyright (C) 1986 ArtTrack (tm) Robert Holmgren 410 Central Park West, 11A New York, New York 10025 Voice: (212) 749-7882 Messages: Manhattan South BBS (212) 432-7288 UpDate User's Manual UpDate Introduction. ------------ UpDate automatically identifies and makes exact byte-for-byte COPYies (or DELetions) of files newly-created or changed since the last time you executed the UpDate procedure. UpDate is a general purpose utility, for use with any or all of your hard-disk directories or high-capacity floppy diskettes. UpDate is superior to DOS's BACKUP utility, or to manual COPYing, because it possesses intelligence and rigorous economy, it copies only what must be copied, it is broadly configurable, precise to the minute (rather than the date), universal across your system, and entirely automatic. Backups do not need to be RESTOREd. You control UpDate. You pre-select (with a configuration file called PATHS.CNF) the range of files to back-up (as well as specific filenames within this range to Skip and not back-up). At runtime you copy, skip, or delete files. You may copy to/from single or multiple hard-disks, high/low-capacity floppy drives, or RAM disks. Dates and times may be altered to recapture files and repeat backup routines from any previous date in time, to any backup destinations (floppy and/or hard-disk). UpDate offers a unique, fast hard- disk alternative to the usual "swap-floppies" back-up routine, even on a single hard-drive: "Parallel destination directories". Especially for frequent modem downloaders, an UpDate sub-system (UPDATE N) locates and copies files of older date which have been newly added to your monitored directories. UpDate incorporates a screen editor, and self-tests, which simplify the processes of installation and operation. UpDate is fast. You can back-up all files across all directories with three keystrokes. UpDate scans directories, and copies files, at DOS speed; the computer's central processor establishes the speed limit. UpDate is NOT SUITABLE for a floppy computer system equipped only with low-capacity diskette drives! (page 2) UpDate User's Manual How UpDate Works. ---------------- UpDate relies upon ordinary DOS v2.x/3.x commands to copy or delete files. All UpDate functions are executed from DOS batch files, and there are no hardware calls, resulting in maximum portability among IBM-compatible computers. UpDate consists of two system files. UPDATE.BAT initializes the program, and opens a chain of batch files. UP.EXE directs all logical operations (sorts, timers); it also writes a .COM file and several other batch files, which are deleted when the program terminates. UP.EXE is an IBM BASICA file compiled with the IBM BASIC Compiler (v1.0 for smaller, faster code). [See also UpDate version summary appended to this Manual.] Preliminary, for Experts. ------------------------ This PROLIX.DOCumentation was originally prepared as part of a commercial inventory control package for museum, gallery, and art professionals who are, in general, aggressively non-technological. A "friendly" orientation to novices persists in the current revised docs (cf. TERSE.DOC for a brief summary). The program implements a large set of user-defined variables which control source and destination drives, directories, and files. This power is inherently complex; the documentation explains it carefully. Although you are expert, please review the following material, because the conventions which UpDate observes are not universal or "similar to" other programs. Proper one-time installation pays off in daily hands-off execution. Preliminary. ----------- Before you begin to use UpDate, it's an excellent idea to designate each of your hard-disk directories and floppy backup diskettes to contain a related group of files. As a practical matter, system files like COMMAND.COM and UP.EXE are never changed or rewritten; they will not need to be copied again after an initial backup is made (unless there is a diskette failure), so you can group permanent files together on several backup disks and put those floppies on ice. Remember, however, that your own "user files" will enlarge and eventually outgrow any initial backup diskette organization, so leave plenty of empty space on user diskettes. Establish logical groups of backup diskettes for all your programs, e.g. your word processor and spreadsheet, or for your directories. Use UpDate once per day. If your systems, especially your floppy drives, are prone to error, also use DOS's DISKCOPY utility on a regular basis, to make second backup diskette copies of your first backup diskettes (page 3) UpDate User's Manual (diskettes are intrinsically less reliable than a hard disk). REMEMBER: Every experienced computer user has lost data in a hardware or software crash. You are not going to be the exception, so don't be complacent. However reliable your machine and media have been, their time will come, sooner or later. UpDate is not memory-resident. It requires approximately 76K of RAM when invoked; during operation UpDate will utilize (briefly, and then relinquish) a variable amount of disk space in the UpDate module directory (typically 5 to 50K). Dates and Times. --------------- UpDate assumes that your computer knows the CORRECT current date and time. If your computer does not automatically keep track of the current date and time, you MUST enter these two figures with reasonable accuracy when you power-up your computer -- otherwise, UpDate WILL NOT WORK (place DATE and TIME statements in the root directory's AUTOEXEC.BAT file, and answer the prompts accurately each time you begin a computer session). Remember, if for any reason you mis-calibrate DOS's intrinsic DATE or TIME functions, or if you deliberately advance UpDate's record of the "last" backup date and time, UpDate may fail to backup files. UpDate's own internal "LASTDATE clock" [not the DOS clock] comprehends the period 1 January 1977-31 December 2076. Do not attempt to set this UpDate clock to a future date (i.e. a date subsequent to the "current" date recognized by DOS); UpDate will reject it. U.S.A. Time/Date Formats: UpDate REQUIRES that DOS directory date/time formats, e.g. "11-19-86 11:02a", conform to those of the U.S.A. (the default setting of most IBM microcomputers; otherwise place the statement COUNTRY=001 in your CONFIG.SYS file). This does not prevent use of a non-USA keyboard: load your keyboard of choice as KEYBxx in your AUTOEXEC.BAT file (v. the DOS manual section "KEYBxx Load Keyboard Command"). First-Time Setup/Configuration of UpDate. ---------------------------------------- Console prompts explain most procedures. The UpDate module files are: coordinator UPDATE.BAT, and UpDate processor UP.EXE. Additionally, UpDate will configure (on its first run, with data which it interactively obtains from the user) a "path specification file" PATHS.CNF. For its own internal use, UpDate will create (again, with user (page 4) UpDate User's Manual input) and maintain a set-up parameter and date/time record called LASTDATE.CNF.1 INSTALL the two UpDate module files UPDATE.BAT and UP.EXE together in a single hard-disk directory or subdirectory, on any drive. Buffers: A reasonable number of disk buffers (determined by a BUFFERS=<number> statement in boot file CONFIG.SYS) will dramatically accelerate UpDate operation, and may affect many or all of your other programs. Typical statements are BUFFERS=15 for a ten megabyte hard-drive, or BUFFERS=30 for a twenty meg drive. You can roughly determine the optimum number of buffers for your computer by stopwatch timing the operation of DOS utility CHKDSK with different BUFFER=n statements. Too many or too few buffers can both retard computing speed, so fine-tune. The UpDate Path Specification File PATHS.CNF: Description. ---------------------------------------------------------- File PATHS.CNF informs UpDate which source drives, directories, sub- directories, or filenames you have elected to back-up on a regular basis. Usually these will be the active disks, directories, and/or files with which you work every day. Before using UpDate you MUST describe, in PATHS.CNF, as much of the directory structure of your hard (or high-capacity floppy) disk(s) as you wish to UpDate on a regular basis. Usually, you create PATHS.CNF before your first use of UpDate, and then forget about it. UpDate's built-in editor collects -- then organizes, re-writes, and tests -- data which you provide to this PATHS.CNF file. You supply PATHS.CNF with as many as 256 path or path + filename specifications, or as few as 1 (an advantage of UpDate is that the range of files backed-up regularly can be very broad, or precise and narrow). These "path specifications" define the directories and files which UpDate will monitor regularly, and backup as required. The largest specifiable PATHS.CNF instruction is to copy a whole directory; the smallest instruction is to copy one file. You may not specify an entire drive, except by mentioning all (sub)directories on that drive. ____________ 1 The following filenames are reserved for the exclusive use of UpDate; do not locate any other files with these names in the UpDate module directory: UP.EXE; UPDATE.BAT; PATHS.CNF; LASTDATE.CNF; ARCH-UPD.CNF [UpDate `N' option only]; ZQ*.* . (page 5) UpDate User's Manual You may backup source files on several source drives. If you choose, you can specify particular filenames to backup with UpDate, and/or use the DOS universal wildcards "?" and "*". If you specify a directory path without filenames, every new file in the specified directory is UpDated, with two important exceptions: ALL files which have the extensions .BAK or .TMP (superceded files usually preserved by a text editor) are deleted from every indicated directory as a cleanup and conservation measure. If, however, you specify particular filenames or extensions including any combination of the wildcards * or ? (e.g. the "all files" designation "*.*", which is the functional equivalent of specifying a path without filenames), then no .BAK or .TMP files will be deleted. You may type path specifications in UPPER or lower case (UpDate path test utility UPDATE T translates all characters to UPPER case). Every path specification begins with a foreslash (e.g. C:\), which indicates that paths to the source directory or filename(s) are specified from a drive's root directory (regardless of whether the UpDate module itself is located in the root or in another directory, on the specified drive or on another drive). Each specified path can be described in 72 characters WITH filenames, or 59 characters WITHOUT filenames (no blank spaces permitted, except in below-described "skip", "hard-only", and "floppy-only" filename specifications).2 Note that you must specify all directories which you wish to UpDate, including the current UpDate module directory, or the root directory. You may specify exceptional `Skip' filenames, within a broader back-up category, which should NOT be backed-up. Some programs incessantly re-write inconsequential auxiliary files, which really need never be copied; it is annoying to confront them each time you UpDate. Other programs produce new indexes whenever a datafile changes; but the datafiles alone may be able to generate these indices at any time, so in some cases (depending on the program) you can back up the datafiles and "Skip" the indexes. UpDate further enables you to limit the backup destination of whole source directories to either hard or floppy disks, by means of specifications in PATHS.CNF: see section entitled Floppy-Only and Hard-Only Path Specs, at the end of this manual. ____________ 2 Avoid long strings of intricate, literal sub-directory names like \ADMINISTRATION\INVENTORY\ACCOUNTING\RECEIVABLES\DEADBEATS, which are designed for novices but excruciating for everyone: use instead brief mnemonics like \ADMIN\INV\ACC\AR\BUMS, or better yet \AD\I\A\R\B. (page 6) UpDate User's Manual Configure path specifications in PATHS.CNF: Procedure. ------------------------------------------------------ In the UpDate module directory, from DOS, type UPDATE T <carriage return> (the "Enter" key, hereinafter called <cr>). Note the space between UPDATE and T. If no PATHS.CNF file currently exists in the UpDate module directory, UpDate loads an editor that prepares a PATHS.CNF file for you. Each path (or narrower path + filename) specification occupies a separate line in the PATHS.CNF file, and has the same format. Enter first the single-letter designation of the drive on which the source directories or files to be backed-up are located [e.g. C]. UpDate will immediately display this drive letter plus the syntactical characters :\ and then invite you to complete the full path specification. Enter a lone <cr> if you wish to specify the root directory only (e.g. C:\); otherwise write the rest of the path specification (e.g. C:\TEXTS), then <cr>. If you make a mistake in one specification, write it correctly in the next specification, then delete the bad line when given an opportunity to edit your file at the end of this procedure. Enter an exclamation point ! to Quit (no <cr>) when you finish entering new lines. To Skip particular filenames (assumed to be included within more encompassing path specifications), write a normal path spec (one of 256 maximum) indicating the complete drive:\path\filename[.extension, if one exists] -- NO wildcards are permitted in Skip specs! Then add a single blank space, plus an ampersand and letter S ( &S). UpDate requires a separate "Skip filename specification" for EACH individual file to be skipped. Example specifications with gloss: C:\ (copy all files in the root directory) C:\A (copy all files in directory \A) C:\A\CONTROL &S (a "skip filename specification" [with appendage &S] for file CONTROL [no EXTension] in directory \A; all other files in \A will be copied) C:\B\*.DAT (copy all \B directory files with extension .DAT) D:\WEIGHTY.TOM (copy only file WEIGHTY.TOM on the D: drive root directory) D:\BOOK\*.* (copy all files in D: drive directory \BOOK, using *.* wildcards to prevent automatic deletion of .BAK and .TMP extension files) D:\BOOK\CHAPTER?.TXT (copy chapter numbers 1-9 using ? wildcard) C:\NAOMI\ART\INDIAN (copy all files in sub-directory \INDIAN with path from the root directory described as \NAOMI\ART\INDIAN) (page 7) UpDate User's Manual Observe that, in PATHS.CNF, you give no direct instructions to the system; you do not indicate any operations (e.g. COPY) to execute, nor do you state the destination drive or directory for those operations, because UpDate performs all these functions for you. You simply describe PATHS from the ROOT to the DIRECTORIES and/or FILES which serve as sources for UpDate. (The directory you select as the actual location of the UpDate utility is irrelevant.) In practice, users who require very tightly-defined PATHS.CNF files have two choices: either to specify only those individual path + filenames which will be monitored, or else to specify broader directory or filename categories and then use "skip filename specifications" to exclude unwanted files. In most cases, the preferred choice is a liberal use of "skip filename specifications", simply because you cannot anticipate the names of files which you may create in future, but you will undoubtedly wish UpDate to find and copy (or at least signal the fresh presence of) those new files; whereas it will be clear from the outset that certain existing files are of no importance to you and can be skipped (the presence in PATHS.CNF of 40 or 80 "skip filename specifications" has no discernible effect on UpDate processing speed, but many narrow copyfile specifications will slightly prolong file-scanning and -sorting at the outset of the UpDate procedure). On the other hand, if you have a byzantine directory organization and wish simply to monitor a few files in each directory, then specify filenames to copy. Edit a pre-existing PATHS.CNF file. ---------------------------------- Type UPDATE T from DOS. The screen offers three options: select the first, E for Edit <cr>, and look at your existing list of specifications. To edit (change) a line, enter the line number <cr>, then re-write the line in its entirety following the Configure procedure described above for brand-new PATHS.CNF files. To delete a line, enter the line number <cr>, then type a minus sign - (no <cr>!). To add a line, enter the next unused line number (as indicated in the screen prompt) <cr>, and append a new line to the file. Each time you add or modify a line in the file, the entire file is re- displayed in its new form, for perusal. You may edit, append, and/or delete as many lines as you choose, in any order. (You cannot insert a new line in the middle of the file, because UpDate will shortly alphabetize the specifications in PATHS.CNF, rendering any user-specified order moot). Type Q <cr> to Quit editing. UpDate now tests your PATHS.CNF file for validity. (page 8) UpDate User's Manual Test validity of PATHS.CNF. -------------------------- You MUST repeat the error-trapping UPDATE T program until you achieve an error-free PATHS.CNF file: UpDate will crash (!) without a valid PATHS.CNF, and it will run slowly and very erratically if UPDATE T has not been allowed to re-organize PATHS.CNF prior to first use.3 UPDATE T is an indispensible (one-time, hands-off) Test utility. It re-organizes and re-writes PATHS.CNF on disk, and then makes sure that each listed path actually travels from the root to its targeted source directory or file(s). If you have just edited or created a PATHS.CNF file, testing ensues automatically whenever you Quit (or `!'). You can test an existing PATHS.CNF file by typing UPDATE T <cr> from DOS, and then selecting the second of three options, Test, by entering a lone <cr>. If your PATHS.CNF file is error-free, UpDate signals "ALL PATHS OK!" on completion of the Test; if there is an error, UPDATE T halts and points to the first bad path it encounters. Study the examples above, or read the DOS manual section "Specifying the Path to a File", if you have trouble with path syntax. N.B.: The UPDATE T test does not evaluate "Skip filename specifications" [ &S] for validity (the proof will reside in the pudding only). Note: Two special situations may cause UPDATE T to flag a path as "bad": 1) If, at the end of a path, you specify a filename which has no extension, e.g. C:\ART\OBJECTS, UpDate is unable to tell whether OBJECTS is a sub-directory of directory ART, or a filename with no extension called OBJECTS which exists in directory ART -- by convention, UpDate defaults to the former assumption (that OBJECTS is a sub-directory), and UPDATE T crashes if OBJECTS is actually a filename. Solution: To distinguish the two, write filenames with no extension in the form C:\ART\OBJECTS.*, adding a ".*" wildcard extension. ____________ 3 Although you may write PATHS.CNF with a text editor or word processor instead of UPDATE T's editor, you must re-organize and Test the file with UPDATE T before use! Beware of word processors (e.g. Wordstar) that do not normally write clean ASCII text to disk. (page 9) UpDate User's Manual But: Do NOT (!) add wildcards or superfluous extensions to "Skip filename specifications" [ &S]; enter each individual Skip spec in PATHS.CNF precisely as it appears in the DOS directory, with or without an extension, and then append " &S" to the line. 2) Directories which contain no files at all, or which do not presently contain a file of the type specified, are always flagged "bad directories" by the UPDATE T test utility, even if they are properly described in PATHS.CNF. Moreover, UPDATE T halts and will not test the remainder of PATHS.CNF. Solution: Copy one file into every empty directory, before testing paths; or place in the directory one real filename of the categorical type (e.g. *.DOC) specified, as a dummy that fulfills the test's need to find such a file present (e.g. re-name an existing file temporarily). Note: UpDate itself (not UPDATE T) will copy files from (empty at test-time) directories or filename specs without difficulty, and it will ignore those specs if they remain empty. (page 10) UpDate User's Manual Run UpDate ---------- To start UpDate: Situate in the UpDate module directory by means of DOS command CH[ange]DIR[ectory] DRIVELETTER:\DIRECTORYNAME, e.g. CHDIR [or CD] C:\A if UpDate is located in dir C:\A N.B. NEVER load UpDate from a different directory. Type UPDATE <cr> at the DOS system prompt.4 After a brief interval during which your diskfiles are scanned and listed off-screen, in normal UpDate operation you are asked whether you wish to change UpDate's record of the Date/Time of the last UpDate procedure. Normally you strike any key other than Y[es] (no <cr>), to omit this option. You then type 1, 2, or 3 (no <cr>) in response to a question: "Back up to hard disk [=1], floppies [=2], or BOTH [=3]?" UpDate then executes. In many configurations, no further action is required of the operator unless you are swapping floppy disks. File-copying is automatic. Date and Time File LASTDATE.CNF. ------------------------------- If you are running UpDate for the very first time, UpDate poses (and then records semi-permanently in a file called LASTDATE.CNF) four set-up questions concerning your floppy/hard drive designations, backup directory organization, and the level of copy/skip control to be exercised over UpDate. The program also solicits a Date and Time that serve as a terminus ad quem for the UpDate processor, an estimate of when you "last" UpDated your files. Like PATHS.CNF, LASTDATE.CNF set-up is usually a one-time affair (unless you change your system or choose to experiment with different possible configurations, in which case the LASTDATE set-ups can easily be changed whenever you run UpDate). You can optionally establish a new "last" Date and Time (and/or change the set-up parameters) anytime you run UpDate, from within the program itself. ____________ 4 You may, for speed, re-name UPDATE.BAT to a shorter or different name such as U.BAT (load as U <cr>; load UPDATE T as U T <cr>). But NEVER re-name UP.EXE. (page 11) UpDate User's Manual The four LASTDATE.CNF set-up questions: 1) UpDate solicits the designation of the floppy disk drive to which floppy back-ups, if any, will be sent. Enter this as a single letter, e.g. A, B, or any other drive-letter through Z. Enter a lone <cr> if there will be no floppy copying. 2) Indicate the drive designation of your hard back-up disk, if any. Generally, make no entry <cr> unless you have more than one hard-disk, more than one hard-disk "logical" drive, or a virtual (RAM) disk. Designate a single hard-disk back-up drive with a single letter, e.g. D, E, or any other drive-letter A through Z. Enter a lone <cr> if there will be no copying to other hard-disks. 3) Define the hard-disk directory organization which UpDate will observe during operation, as explained at length in the discussions of "Parallel hard- disk back-up directories" and "Copying between Two Drives", q.v. below in the section entitled Drive and Directory Organization. In brief, this question asks whether UpDate shall send back-ups to: a) "Mirror-image directories" which bear the same directory names as their sources, on one different backup hard drive [= M <cr>]; b) "Parallel backup directories" which bear slightly different directory names than their sources, and are located on the same drive as the source files [= P <cr>]; or else shall UpDate c) Collect backups in one catch-all root directory on either a single different hard drive (designated in question #2, above) or on floppies only [= R <cr>] ? For first-time use, default to Root directories only (R <cr>). You may wish to change this entry (easily done) after you learn what it means. Note that, if you select Mirror-image or Parallel directory organization on your backup hard-disk, and during operation also send back-ups to floppy diskettes, UpDate will collect floppy back-ups in the floppy Root directory only! In other words, Mirror-image or Parallel directories will be sought ONLY on hard-disk backup drives, not on the floppy drive. Backup floppy diskettes are always assumed by UpDate to possess a single root directory only (but note that there are several ways to circumvent this assumption, one of which is referenced in the first paragraph of the section entitled General Considerations, below). 4) UpDate then asks whether you intend to use "Universal" or "Selective" Copy Mode, explained in the following section entitled Universal or Selective (page 12) UpDate User's Manual Copy Modes. First-time users should enter S for "Selective" mode (this is always adjustable at runtime). In "Selective" mode, you'll be able to skip all copying operations, on your initial use of UpDate, if your set-up is faulty. An important chart at the back of this manual describes typical system configurations with their corresponding LASTDATE.CNF entries. The two LASTDATE.CNF Date/Time questions: UpDate's internal "clock" sets the Date and Time of the "last" back- up routine. Console prompts illustrate the correct form for Date and Time statements.5 On this first-time run, it's a good idea to set the date back a few days, to copy numerous files and learn how UpDate works. LASTDATE.CNF need never be set manually again. In future, UpDate will automatically keep track of the last backup time, and continuously copy new files as necessary. But anytime you wish to repeat the backup of, for example, yesterday's or last week's files, simply change the date, when offered the option to do so at the start of the UpDate routine, and enter a date which precedes the time you created the files that are to be UpDated again (e.g. yesterday morning at 0000 hours [Midnight], just to be sure that you catch all of yesterday's transactions). Altering the "last" date has no lingering effect upon UpDate, because UpDate will backup everything that has happened (in the directories specified in PATHS.CNF) from e.g. yesterday morning until the present moment, and it will then make an internal note of the current, correct Date and Time. If in hindsight you decide that you don't really wish to change the "last" Date/Time, you can Abort to the existing LASTDATE.CNF record of these values by typing A <cr> at the first "last backup date" prompt. NEVER erase file LASTDATE.CNF from a directory or floppy, unless you wish to alter the destination drive designations for floppy and/or hard-disk UpDates! If you need new LASTDATE.CNF drive or directory configurations, elect to change the Date/Time when you run UpDate, then enter L <cr> in response to the "last backup Date" question. This will permit you to re- create a LASTDATE.CNF file from scratch. If you regret this choice, you can Abort to your existing LASTDATE.CNF file with A <cr> when the "last backup Date" prompt reappears again after entering dummy responses to the first four LASTDATE.CNF set-up questions; no new LASTDATE.CNF file will be logged on ____________ 5 UpDate uses European date and time formats: DDMMYY (day month year) and HHMM (hour minute). (page 13) UpDate User's Manual disk. Repeat the four set-up questions by entering L <cr> at the "last backup Date" prompt, until you are satisfied that your responses are error-free. Universal or Selective Copy Modes. --------------------------------- UpDate offers the option of "Universal" or "Selective" copying: type 4 (and then select backup destination 1, 2, or 3), to toggle between Universal and Selective copy modes. "Universal" means that every new or changed file is copied to hard- disk and/or floppy backup areas. Leaving the UpDate processor permanently in "Universal" copying mode is the safest and often fastest method of backing up all files; furthermore, a degree of copy/skip control is still exercised with PATHS.CNF "skip filename specifications". In "Selective" copy mode, UpDate pauses to enable a deliberate decision about each file, whether to copy it, delete it, or skip it. UpDate then proceeds to the next file awaiting copying, to make the same decision again. You must hit the "Y"[es] key to copy, or the minus sign "-" to delete, the source file; all other keys are omit-copy or "skip" instruction keys. Users who understand the inner file structure of their programs and disks, who tinker extensively or create a separate file for everything, or possess cluttered disks short on space, may find that "Universal" mode lacks flexibility. They save time and space by "Selectively" copying only those files which have truly changed or are important, and deleting those which are superfluous. N.B.: The Delete option is available ONLY in "Selective" copy mode. To delete a file, you must hit a minus sign (-) key twice, as a precaution against fatal user-error (abort deletion by hitting any other key than a minus sign at the second delete prompt). "Delete" erases the source file only, not files of the same name on destination directories or disks. If you ABORT deletion at the second delete prompt (by hitting any other key), the opportunity to instead Copy that file is lost. If you are backing up both to floppies and hard-disks, and abort deletion on the first (floppy-copy) opportunity, you may still copy to the hard disk, but you can no longer delete the file (a minus sign `-' yields a skip). Deletions are final, and unrecoverable with DOS [try Norton's UNERASE utility, to restore a file]. Run UpDate (continued). ---------- Send your backups this first time to floppy disks only: select backup destination 2. Then repeat the process with hard-drive back-ups only (if you (page 14) UpDate User's Manual use them), by backdating again at the start of the UpDate program to the same date a few days ago, and selecting backup destination 1. This experiment will indicate the varying times consumed by the two procedures. Regardless of destination, a list of files that were altered or added since the last time you UpDated passes by the screen twice, the first time for informational purposes only (file sizes, etc), the second time as copying operations proceed. This, by the bye, is often valuable, because you are reminded of a day's work and alerted in passing to things you forgot, the files that should be deleted, the correspondence left in limbo. Changed files which will be omitted due to PATHS.CNF "skip filename specifications" are also listed on the first pass, with the label [SKIP] appended -- as an advisory. Anomaly: The UpDate processor writes an up-to-date LASTDATE.CNF file in the UpDate module directory only after it searches through the directories specified in PATHS.CNF and finds at least one new or changed file. If LASTDATE.CNF is encompassed within a PATHS.CNF source specification, i.e. if you specify the UpDate module directory itself in PATHS.CNF or specify a different UpDate module in another directory, LASTDATE.CNF will appear in the first advisory screen listing of files; but if no other new or changed files are found, UpDate will end with the message "No Files Were Changed Since Last UpDate", and the previously-existing LASTDATE.CNF will remain the file of record. Whenever you copy in "Universal" mode and respond to the UpDate processor's destination question with 1 [UpDate to hard-disk backup directories only], you are finished with UpDate; the computer takes over and performs a series of copying operations, which are listed on screen as they occur. If, in Universal mode, your response to the destination question was 2 (back up to floppies only) or 3 (back up to BOTH hard disk and floppies), UpDate will "pause" before each file to be copied, to permit you to insert in the floppy back-up drive the correct floppy diskette. "Strike a key when ready", i.e. after you have inserted the disk in the floppy drive and locked the drive latch. The name and destination drive\directory for each file to be copied are displayed on screen, to enable selection of the right floppy. If you do not need to switch disks, simply <cr>. If, in Universal mode, you pick destination 3, copies are simultaneously and automatically made to the designated hard disk backup areas. In Selective mode, respond either "Y"es to Copy, "-" to Delete, or any other key (an implicit "Omit Copy"), for EACH copy operation, both hard-disk and floppy. Swap floppies first, if you intend to copy. Before writing a copy on floppies (destinations 2 and 3, both modes), the UpDate processor checks to see whether the file already exists on the (page 15) UpDate User's Manual floppy back-up disk that is inserted. If UpDate does not find the file on that diskette, a "WARNING" message is displayed. You MAY have the wrong disk in the floppy drive. You are given ONE opportunity to switch floppies, if required. (Naturally, if the file is brand-new, no backup will exist on any diskette, so hit any key to proceed with copying.) Caution: if you interrupt (crash) UpDate at any point (with <Ctrl+Break>, <Ctrl+C>, or <Ctrl+Alt+Del>), files may not be copied! The rule is, don't crash deliberately. UpDate's internal Date/Time records may have been reset, without actually having completed the file-copying routine. The best procedure is always to pencil a note of user-errors, continue the UpDate routine as usual, and then repair mistakes manually (or re-run UpDate). Be sure to back-date the next time you use UpDate if a crash occurs. (page 16) UpDate User's Manual Drive and Directory Organization. -------------------------------- 1) Parallel hard-disk backup directories on single hard-drive systems. ---------------------------------------------------------------------- Theory: If you have one hard-disk drive only, UpDate offers an optional enhancement to your directory organization, a duplication of files which is costly in disk space and may seem over-cautious, but which you will find both prudent and useful in any environment that drives its computer intensively. UpDate can create, for every master directory or subdirectory mentioned in PATHS.CNF, a Parallel hard-disk backup directory or subdirectory on the same hard-disk drive. This yields (among other advantages) an ultra-high-speed/hard-disk-only backup system, with a capability of subsequently backdating to the last floppy UpDate procedure and thus bringing your floppies "up-to-date", at any time. However, it cannot be used if you do not have plenty of available hard-disk space, equivalent at least to the combined size of all the files you will be backing up. "Parallel hard-disk backup" operation is selected by responding P to the LASTDATE.CNF directory definition question #3, described above. The Parallel hard-disk directories are created (before first use of UpDate) by means of the MBD (Make Backup Directories) option of UPDATE T, as described below. UpDate views this Parallel directory structure as highly advantageous, rather than restrictive. In reality, rigorous "backing up" of a hard disk has meant, in the past, either switching dozens of floppies for 10-30 minutes/day, or down-loading to a streaming tape system which protected your data if the computer failed, but was impractical as a substitute read/write medium when you needed to recall one old file or your hard disk was being repaired. People who were unwilling to take the time to swap floppies (the vast majority) didn't backup -- period. But backing up serves more purposes than simply protecting against media failure. In fact, about 99% of backups recover from accidental erasure, or bad-judgment alteration, of files. UpDate's optional Parallel directory structure offers a compromise solution for single hard-disk systems that can bring your floppies "up-to-date" whenever you wish. It will allow you to recall older versions of files at any time, or consult a complete second fileset. It will NOT protect your data in case of total hard-disk failure, so back-up to floppies with a frequency which you feel is prudent. Procedure: If the UpDate module directory is specified in PATHS.CNF, then each time you execute UpDate to floppy diskettes, a copy of the current Date/Time (page 17) UpDate User's Manual file will be written (unless you omit it in Selective copy mode) upon one of these floppy disks (filename LASTDATE.CNF [no .EXTension]). Suppose that you subsequently decline to copy to floppies for one or more UpDate routines, and instead backup only to the Parallel hard disk directories (for hands-off convenience and high speed). You can bring your floppies up-to-date by manually copying the LASTDATE.CNF file from this diskette to the main UpDate hard-disk directory.6 Then run UpDate as usual, sending copies to floppies only. All files written since the last floppy UpDate procedure will be copied to floppies. Each independent Parallel back-up directory is nested at the same tree-level as the master (source) directory or subdirectory which it backs up. It bears a name which is identical to the name of the path from the root directory to the source directory, plus the numeric suffix "1". Thus, for example, a C:\ART master directory has a Parallel back-up directory labelled C:\ART1. The only exception to this "Suffix-1 rule" applies to a drive's root directory which, because of DOS conventions, must be totally renamed: UpDate calls this root directory Parallel backup area [DRIVELETTER]:\D, e.g. C:\D. A Parallel hard-disk backup directory need not contain programs or control files which never change (although it's often convenient to have a complete second system available anyway); for purchased programs, you probably already possess at least two floppy backups (the original and your copy). If you don't have much extra space on your one hard-disk, don't cram backup directories with "system files" because they never change. N.B.: Always enter path designations in PATHS.CNF for your master source directories only, and not for any backup directories. Parallel hard-disk backup directories: Installation. ---------------------------------------------------- UpDate creates (hands-off) these hard-disk backup directories for you, but don't make them until your PATHS.CNF file has received the ** ALL PATHS OK! ** blessing from UPDATE T's path tester. Then load UPDATE T from DOS, and select the "MBD" (Make Backup Directories) option, which will automatically create Parallel back-up directories on the same hard-drive, for all specified source drives. ____________ 6 UpDate can't perform this chore automatically, because UpDate doesn't know which of your floppy diskettes contains the LASTDATE.CNF file, and we elected not to impose volume labels on your floppies as a means of identification. Therefore, UpDate relies upon you to find the proper diskette and restore LASTDATE to your UpDate module directory: from the UpDate directory, syntax COPY [FLOPPYDRIVELETTER]:LASTDATE.CNF [HARDDISKDRIVELETTER]: thus e.g. COPY A:LASTDATE.CNF C: (page 18) UpDate User's Manual It doesn't matter if some (or all) of these backup directories already exist (e.g. if you are adding new backup directories to a pre-existing set), because UpDate will ignore a "Make Directory" instruction with the message "Unable to create directory" for those directories already in existence. N.B.: If you leave the hard-driveletter designation blank (LASTDATE.CNF question #2) and also leave the directory definition blank (LASTDATE.CNF question #3), no other destination options than floppy backup are offered. Copying between Two Drives. -------------------------- Preliminary. UpDate will copy source files from one hard drive, to destination directories on another hard drive (or from one floppy to a second floppy drive). Another identical hard drive is, after all, the ideal backup vehicle! See 2) below. "Another" hard drive means also "logical" drives, i.e. single hard drives which have been subdivided into several separate "logical" drive designations (e.g. C:, D:,...Z:): see 3) below. RAM drives, or virtual memory "drives" which mimic logical drives and possess separate driveletter designations, are also included in this category: see 4) below. With some restrictions, floppy systems may also use UpDate: see 5). UpDate's only limitation when copying between two or more "drives" is that it sends every copy without exception, from whatever source, to ONE other hard drive destination. You could not send, from an UpDate module on C:, file X to D: and file Y to E:. But you could establish on C: two separate UpDate modules, one with a D: destination and the other with an E: destination. Additional copying to floppies is encouraged. (page 19) UpDate User's Manual 2) Copying between Two Hard Drives. ----------------------------------- The directory(ies) to which files are sent on the backup drive is selected in LASTDATE.CNF directory definition question #3. When copying between two different hard drives, you have two choices: M for "Mirror-image directories"; or R to collect all backup files in the Root directory, regardless of source directory: M: = Mirror-image. A "Mirror-image" of the source hard-drive means that the (sub)directory "tree" of the source drive is replicated precisely on the destination drive (at least with respect to those directories which UpDate will back-up: e.g. if C:\ART\LETTERS is a subdirectory of C:, UpDate looks on back-up drive D: for a D:\ART\LETTERS subdirectory).7 Procedure: Configure PATHS.CNF source definitions as usual. Create directories on your backup hard drive identical to those on your source hard drive [MKDIR for every (sub)directory]. Create a new LASTDATE.CNF file (run UpDate and enter Y to change the date, then L <cr> at the first prompt to revise LASTDATE.CNF designations). Enter drive designations for your floppy drive (if any), and for your back-up hard disk, as prompted by UpDate. Enter directory definition M. Re-set "last" Date and Time, then proceed normally. Note that, in Universal mode, backing up to the hard-disk only (destination option 1) results in fast hands-off operation. R: = Root directory only backups. Suppose that you wish to copy files from various discreet subdirectories on e.g. C: [and/or E: and F: etc] to one large catch-all back-up "holding area" in the e.g. D: root directory. In other words, you don't wish or care to have a Mirror-image of your source directories on D: Procedure: Configure PATHS.CNF source specs as usual. Write a new LASTDATE.CNF file. Enter (optional) floppy and hard back-up drive designations. Then enter R as the directory definition. All files from all drives and directories will be copied to D:\. ____________ 7 N.B.: Back-up directories on different hard drives may NOT be "Suffix-1" directories: "Suffix-1" Parallel directories are used only when backing up to the same hard drive! (page 20) UpDate User's Manual If you leave LASTDATE.CNF's floppy drive designation blank (in either copy mode), no other destination options than hard-disk backup are offered. 3) "Logical Drive" Systems (usually one actual hard drive) ----------------------------------------------------------- If your system consists of various "logical" drives, i.e. one (or more) hard drives subdivided into various "logical" drives or "partitions", each of which possesses a separate driveletter designation, you may use one of your "logical" drives as a back-up area to collect all back-ups from the other "logical" drives (observe that this is the functional equivalent of Parallel "Suffix-1" backing-up -- with the same advantages and disadvantages -- but the directory definition in LASTDATE.CNF question #3 will be R rather than P). It is always a good idea, on a one hard-drive system, to make floppy back-ups also, for protection against a hard-disk crash. 4) Virtual [RAM] Disks. ----------------------- UpDate is an ideal RAM disk back-up. Do your daily work on a RAM disk, for lightening speed. At the end of a session, before cutting power to the computer, run UpDate and store all new RAM files on your hard disk. Procedure: You need not (but could) put UpDate on your RAM disk. However, you require PATHS.CNF and LASTDATE.CNF files configured for use with the RAM disk. Suppose that D: is the RAM disk, and C: is the hard drive: The PATHS.CNF specification might be simply D:\*.* or D:\ Optional LASTDATE.CNF floppy backup destination Set the LASTDATE.CNF hard disk backup destination to C Set LASTDATE.CNF directory definition to M or R In this example, run UpDate off C:, and it will transfer all new files from D: to C:. If you establish several directories on your D: drive RAM disk and use the M "Mirror-image" directory definition, be sure that UpDate finds corresponding ("Mirror-image") directories on C:! (page 21) UpDate User's Manual 5) Dual-Drive or Single-Drive Floppy Diskette Computers (No Hard Drives!). -------------------------------------------------------------------------- UpDate functions on computers with no hard drive. But the usefulness of UpDate is sharply restricted if the floppy drives are small-capacity (e.g. 320 or 360K), because UpDate module files will occupy approximately 76K bytes of space on EACH source diskette (unless you locate the UpDate module on a RAM disk, which is a fine idea), and UpDate will require additional floppy (or RAM) disk space (typically to 50K) during operation. Therefore, UpDate is not recommended for small-capacity floppy-only computer systems. However, with high-capacity diskettes (e.g. 1.2M byte capacity), UpDate may be very useful, because most users organize their diskettes to contain related groups of files, and they often fill a mere fraction of available space on each of these more spacious diskettes. Procedure: Suppose, as most IBM computers do, that A: is the source drive. Whether you have one or two floppy drives, it will be necessary to designate the destination drive as a different drive, e.g. B:, even if the actual destination drive is also A: (DOS will resolve this problem internally): Set PATHS.CNF to read, e.g., A:\ Define LASTDATE.CNF floppy back-up drive as B Define LASTDATE.CNF directory structure as R Run UpDate normally On one-drive floppy-only systems, DOS will prompt you to swap source and destination diskettes as required; when DOS prompts to insert floppy B:, it really means that the destination diskette should be inserted in A: On two-drive floppy-only systems, you can create a "hands-off" copyfile facility by treating the floppy destination drive as a hard drive in LASTDATE.CNF (no "floppy drive" should be listed in LASTDATE.CNF). "Universal" mode yields hands-off operation, while "Selective" mode offers the usual skip/copy option. Furthermore, on a two-drive floppy system, if you set LASTDATE.CNF's directory definition to M (for "Mirror-image" directories), a hierarchical (sub)directory structure on floppy source disks will be maintained on the destination diskettes (an exception to UpDate's usual practice of collecting floppy back-ups in floppy root directories only, made possible because UpDate has been informed falsely that your floppy destination drive is a "hard drive"). (page 22) UpDate User's Manual Comment. ------- Notwithstanding the drive/directory organization, you always have the option of using UpDate to backup only to floppy diskettes (indicate a floppy drive in LASTDATE.CNF set-up parameter #1). Floppy-Only and Hard-Only Path Specs. ------------------------------------ N.B.: These procedures are relevant only on systems which address BOTH floppy AND hard-drive back-up areas. UpDate permits blanket path specifications for whole directories, which restrict them to FLOPPY ONLY [ &F] or HARD-DISK ONLY [ &H] backup destinations. "Floppy-only" and "Hard-only" directory specifications are similar to "skip filename specifications" [ &S], previously described. PATHS.CNF is again the vehicle for these instructions. Suppose that one of your directories (e.g. C:\DATA) contains an important database; you maintain a complete, second backup fileset of this database on both hard-disk and floppies. Suppose further that your OTHER directories and files don't require this degree of backup protection, or that you're pinched for hard-disk space; you elect to back the others up to floppies only. (It sounds like Selective copy mode, but actually it's pre-configured with PATHS.CNF, and it runs hands-off.) Example UPDATE T specifications (with gloss): line # ------ 1 C:\DATA (copy all directory \DATA files to floppies & hard disk) 2 C:\ART (copy all directory \ART files ...) 3 C:\ART &F (but copy them to floppy destinations only) 4 C:\CHINESE\LETTERS &H (copy specified files from subdirectory \LETTERS to hard-disk destinations only, ...) 5 C:\CHINESE\LETTERS\TAN.TXT (for example, the letter to Tan ...) 6 C:\CHINESE\LETTERS\DENG.TXT &S (but skip Deng's letter) "Hard-only" directory specs [ &H] reflect the same concept: file- copying operations are directed to hard-disk destinations only, for the directories and/or filenames specified. Note some conceptual differences when " &F" and " &H" directory specs are used. &F and &H are akin to ENVIRONment statements about whole directories. You must ALSO, first, specify the directories or individual filenames which you wish to monitor and copy, via regular path specs. Thus, the example C:\ART directory specifications above indicate, in line 2, that all files in \ART will be copied (because the entire directory (page 23) UpDate User's Manual C:\ART is generally specified), but in line 3, that they will be copied only to floppy disks (no hard-disk back-up option will be offered). Rule: If you wish to back-up an entire directory, make a general directory specification, and then REPEAT this specification with the appendage " &F" or " &H" (one blank space plus an ampersand "&" plus letter "F" or "H"). The specs for subdirectory C:\CHINESE\LETTERS are different. Only individually specified filenames in \CHINESE\LETTERS will be copied, because there is no general specification for this (sub)directory. The &H spec in line 4 serves no function other than to inform the UpDate processor that individual filenames (e.g. line 5) will be copied to hard-disk backup areas only (no floppy back-up option will be offered). Rule: If you wish to back-up specific filenames only, specify the directory (without any filename) and append " &F" or " &H", then specify filename(s) individually. Wildcards are permitted in filename specifications. N.B.: The UPDATE T test does NOT evaluate "floppy-only" [ &F] or "hard-only" [ &H] directory specifications for validity. Locating and UpDating Newly-Added Files Bearing Old Dates --------------------------------------------------------- If you purchase a new program, and add its files to PATHS.CNF directories, the standard UpDate procedure will not copy them because they will usually bear creation dates which PRECEDE the date/time record in LASTDATE.CNF. But UpDate's "N" option will locate files newly-added to the PATHS.CNF specified directories, which bear dates EARLIER than the date recorded in LASTDATE.CNF. It will also spot new or differently-dated/-sized versions of filenames ALREADY located in your directories, e.g. if you acquire the latest implementation of a program. UPDATE N is practical for modem users, who acquire date-stamped files (via the Ymodem protocol, or from ARChives and LiBRaries). UPDATE N is a SEPARATE procedure, executed from DOS with the command UPDATE N <cr>. N.B.: UPDATE N absolutely REQUIRES the presence of DOS file SORT.EXE in the UpDate module directory. UPDATE N establishes (hands-off on the initial run), and thereafter maintains in the UpDate module directory, an archival file called ARCH-UPD.CNF which serves as a reference for all old-date files. Each time you run UPDATE N, current file listings are compared with ARCH-UPD.CNF, and all newly- (page 24) UpDate User's Manual added files dated earlier than the LASTDATE.CNF date/time record are flagged for copying. A listing of newly-added files is displayed on-screen after your directories are sorted, and you may either abort the UPDATE N procedure, or proceed. If you proceed, UPDATE N operates exactly like the standard UpDate except that filenames listed are all newly-added but dated PRIOR TO the LASTDATE.CNF date/time record (new files dated AFTER the LASTDATE.CNF date/time record are flagged only during standard UpDate execution). Also, you are not permitted to change the current LASTDATE.CNF file, because UPDATE N never re-writes it. You may not elect Universal Copy Mode; the default for UPDATE N is always Selective Mode. Run UPDATE N first, BEFORE you run UPDATE. If you only run UPDATE N occasionally, and not each time you UpDate, UPDATE N may flag files which have already been UpDated during the standard procedure (Skip them). Tip: If you wish always to run both UPDATE N and standard UPDATE simultaneously, create a batch file (called e.g. UPDATEN.BAT) containing the following two commands: [d:\path\]COMMAND/C UPDATE N UPDATE (If COMMAND.COM is NOT located in your UpDate module directory, specify its location in the first line: e.g., if COMMAND is in the root directory, type \COMMAND/C UPDATE N). General Considerations. ---------------------- The last paragraph of Drive and Directory Organization (section 5, "Floppy Diskette Computers", above) represents one of the (sometimes unorthodox) variations by which PATHS.CNF and LASTDATE.CNF can be harmonized to configure a system that works, day-in day-out. A chart at the back of this manual suggests the most typical configurations of LASTDATE.CNF's system definitions. If none of them fit your computer system, experiment! (UpDate will forbid some, but not all, illogical or unworkable configurations.) Remember that the UpDate procedure takes slightly more time as you add more directories and/or multiple filenames within the same directory -- although not "skip filename specifications" [ &S] -- to PATHS.CNF. In an environment of intense use, backing up four or five directories once a day, you may complete UpDate in about 2-5 minutes if you manually switch floppies, and about 1-2 minutes if you back-up only to the hard disk in "Universal" copy mode. (page 25) UpDate User's Manual In both single-user and multi-user (multi-terminal) environments, you can install several UpDate modules in the system, e.g. one for your databases, another for your text files -- or one for each user -- but locate the modules in different directories! Password security should not present a problem, assuming that the user possesses permission to enter each of the directories named in PATHS.CNF and doesn't need to "show" his/her password every time these directories are accessed. Always enter path designations in PATHS.CNF for your master source directories only, and not for any backup directories. UpDate is entirely automatic and self-regulating, but if you opt to back up to floppies, or to both floppies and your hard disk backup areas (either of which will entail some disk-switching), you will want to pay close attention to the prompts which appear. If you make a mistake and copy data onto the wrong backup diskette, either repair this error manually using DOS's COPY command after UpDate is finished, or else re-run UpDate and backdate the procedure. (page 26) UpDate User's Manual Summary of UpDate: First-Time Installation: Install UpDate module programs together in one directory List path specifications in the PATHS.CNF configure file Re-organize PATHS.CNF on disk and then TEST that specified paths actually travel to their targeted directories or files, with the UPDATE T utility Create back-up "Suffix-1" hard-disk directories [if required], with the MBD (or "Make Backup Directories") option of UPDATE T Assign floppy back-up diskettes to logical "groups" of files Run UpDate and set-up LASTDATE.CNF: 1) floppy destination drive; 2) hard-disk destination drive; 3) an M, P, or R directory definition; and 4) Universal or Selective copy mode; Time and Date of "last" backup routine Operation: Set accurate current time & date in DOS on power-up [if necessary] Type UPDATE N <cr> [optional] at DOS level, from within the UpDate module directory Type UPDATE <cr> at DOS level, from within the UpDate module directory Reset time of last UpDate [optional] Choose Universal or Selective copying [optional] Indicate destination for back-up copies (hard-disk, floppies, or both) Prepare to switch floppy diskettes [if necessary] Table of User Variables: Function Implementation -------- -------------- Current Date/Time DOS Alter Last Backup Date and Time Runtime Directory to Copy [Path specification] PATHS.CNF Filename to Copy [Path specification] PATHS.CNF Filename to Skip (Omit-Copy) [ &S Path spec] PATHS.CNF Directory to Copy to Floppies Only [ &F Path spec] PATHS.CNF Directory to Copy to Hard-Disk Only [ &H Path spec] PATHS.CNF Copy Old-Date Files UPDATE N Hard Disk Only UpDate All Files Runtime/LASTDATE.CNF Floppy Only UpDates All Files Runtime/LASTDATE.CNF Floppy AND Hard UpDates All Files Runtime/LASTDATE.CNF Optional Copy/Skip Control [Universal/Selective mode] Runtime/LASTDATE.CNF Delete File [Selective mode only] Runtime (page 27) UpDate User's Manual Typical System Configurations Set-Up Entries in File LASTDATE.CNF | Actual | LASTDATE.CNF LASTDATE.CNF LASTDATE.CNF Source Drv(s) | "Floppy Backup Drv" "Hard Backup Drv" Dir switch M/P/R _________________|___________________________________________________________ 1. Floppy 1 "Floppy 2" [real 1] <nul> R System: One high-capacity floppy drive Purpose: Back-up all floppy files to floppy back-up diskettes _________________|___________________________________________________________ 2. Floppy 1 Floppy 2 <nul> R System: Two high-capacity floppy drives Purpose: Back-up all floppy files to floppy back-up diskettes on floppy drive 2 _________________|___________________________________________________________ 3. Hard Floppy 1 <nul> R System: One hard drive and one high/low-capacity floppy drive Purpose: Back-up all files on all hard drives to floppy diskettes _________________|___________________________________________________________ 4. Hard Floppy 1 <nul> P System: One or more hard drives plus high/low-capacity floppy drive Purpose: Back-up all files on all hard drives to Parallel "Suffix-1" directories on the same hard drive(s) [plus optional floppy copying to the floppy root directory] Advantages: Protection against user-errors, write errors, bad sectors Back-up all files, all directories, all drives High speed Hands-off operation No floppy swapping Disadvantages: No protection against total hard-disk crash Large hard disk-space consumption No portability _______________|_____________________________________________________________ 5. Hard Floppy 1 or <nul> Hard M System: Two or more hard disk drives and (optional) high/low-capacity floppy drive; The Optimum System Purpose: Back-up all files on all source drives to one destination drive (destination must have Mirror-image directories for every path called) (page 28) UpDate User's Manual Advantages: Protection against all hardware/software/user errors Complete "Mirror-image" second fileset High speed Hands-off operation Disadvantages: No portability Floppy swapping (optional) Actual | LASTDATE.CNF LASTDATE.CNF LASTDATE.CNF Source Drv(s) | "Floppy Backup Drv" "Hard Backup Drv" Dir switch M/P/R _______________|_____________________________________________________________ 6. Hard Floppy 1 or <nul> Hard Backup M System: Two or more "logical" hard drives (albeit perhaps only one physical hard drive) plus optional high/low-capacity floppy drive Purpose: Back-up all files on all "logical" source drives to one "logical" destination drive (destination must have Mirror-image directories for every path called) Advantages: Protection against user-errors, write errors, bad sectors (and, with floppies, a hard disk crash) High speed Hands-off operation (no floppies) No floppy swapping (optional) Disadvantages: No protection against total hard-disk crash if one physical hard-drive Large hard disk-space consumption ________________|____________________________________________________________ 7. RAM disk Floppy or <nul> Hard or <nul> M or R System: Virtual disk [RAM drive]; high/low-capacity floppy and/or hard drive(s) Purpose: Back up RAM drive to hard disk, floppies, or both Advantages: Ultra high-speed, in every respect Disadvantages: High RAM requirements ________________|____________________________________________________________ 8. Hard Floppy or <nul> Hard Backup R System: Two or more hard drives Purpose: Back-up all files on all source drives to one destination drive root directory _____________________________________________________________________________ (page 29) UpDate User's Manual Structure of sample LASTDATE.CNF files (length=14 bytes): a = Floppy Drive Designation b = Hard Drive Designation c = Directory Definition d = Universal/Selective Copy Mode e = Last Date f = Last Time coded as above: eeeeeeffffabcd eeeeeeffffabcd -------------- -------------- e.g. for one hard drive YYMMDDHHMMA PU e.g. for multiple hard drives YYMMDDHHMMADMS e.g. for floppy drives only YYMMDDHHMMB RS or YYMMDDHHMM BRU ______________________________________________________________________________ UpDate Version History 1.0 4 Apr 85 1.1 1 Jun 85 Configurable LASTDATE.CNF file Support for multiple hard drives and RAM disks 1.2 12 Aug 85 Extensive docs 1.3 15 Oct 85 Incorporated PATHS.CNF editor &Skip specs Nested conditional batch file logic 1.4 17 Oct 85 Simplified source 1.5 12 Nov 85 Parallel Suffix-1 directories 2.0 9 Jan 86 &Floppy/&Hard-only specs 2.1 22 Feb 86 New screens and docs 2.2 24 Apr 86 UPDATE N option for newly-added files of "Old" date 2.3 29 Apr 86 Revised docs and screens 2.4 9 May 86 Code changes; fixes to UPDATE N (page 30) UpDate User's Manual Index Advantages of UpDate.........................................................2 Append specifications to PATHS.CNF...........................................8 Back-up directories, hands-off method for creating..........................18 Back-up drives, define......................................................12 Back-up drives, define......................................................12 Back-ups, reasons for.......................................................17 BAK files, automatic deletion or preservation by UpDate......................6 Buffers, number to install...................................................5 Change "last" backup Date and Time..........................................13 Clock limits, past and future................................................4 Copy to root directories only...............................................20 Cr, carriage return <cr> or "Enter" key......................................7 Cr, carriage return, abbreviated <cr>........................................7 DATE and TIME functions (DOS), importance of.................................4 Date and time records of last UpDate procedure..............................11 Date/Time formats, must conform to USA (COUNTRY=001).........................4 Delete files, how to........................................................14 Delete specifications from PATHS.CNF.........................................8 Destination directories, define.............................................12 Directory paths, how to specify (UpDate).....................................5 Disk buffers, number to install..............................................5 Disk failure.................................................................3 Dual hard-drive copying.....................................................19 Duration of typical UpDate run..............................................25 Edit PATHS.CNF...............................................................8 Empty directory/filename specifications.....................................10 Enter key <cr>...............................................................7 Erase files, how to.........................................................14 Experimentation, with unorthodox configurations.............................25 Floppy Backup Driveletter, LASTDATE.CNF.....................................12 Floppy diskettes, arrangement of.............................................3 Floppy-disk only directory specifications...................................23 Floppy-disk only, example specifications....................................23 Floppy-Only Systems: installation and use [and Limitations]...............22 Floppy-swapping, pause to enable............................................15 Hands-off hard-disk copying.................................................15 Hard-Disk Backup Driveletter, LASTDATE.CNF..................................12 Hard-disk only directory specifications.....................................23 Hard-disk only, example specifications......................................23 Hard-drive back-ups on single-drive systems (Parallel directories)..........17 History of Backing-Up.......................................................17 Keyboards, USA and non-USA...................................................4 LASTDATE.CNF set-up.........................................................11 LASTDATE.CNF, drive and directory designations, change......................13 Length of UpDate procedure, variables which affect..........................25 (page 31) List of Files, first pass on-screen as an advisory..........................15 Logical drive copying: procedure...........................................21 Logical drives..............................................................19 Mirror-image directories: definition.......................................20 Multi-user considerations...................................................26 N option, locate old-date files newly added to directories...................2 Newly-added files of older date.............................................24 Parallel (Suffix-1) directories, definition.................................17 Parallel directories, installation (with UPDATE T's `MBD' option)...........18 Parallel directories, theory and structure..................................18 Password security, effect of................................................26 Path specifications, definition of...........................................5 Paths, examples of specifications............................................7 Paths, examples of specifications...........................................23 Paths, specifying for UpDate.................................................5 PATHS.CNF path specification file, definition................................6 PATHS.CNF, example specifications............................................7 PATHS.CNF, function .........................................................5 PATHS.CNF, how to specify directories/filenames..............................7 PATHS.CNF, philosophy........................................................8 PATHS.CNF, philosophy........................................................8 PATHS.CNF, philosophy........................................................8 Preliminary preparations.....................................................3 RAM disk copying: procedure................................................21 Re-organize PATHS.CNF with UPDATE T, necessity of............................9 Root directory collects all floppy back-up files............................12 Run UPDATE N and UPDATE together (make a batch file)........................25 Security, effect of.........................................................26 Selective copy mode: description...........................................14 Set-up of LASTDATE.CNF......................................................11 Single-drive hard-disk backup option (Parallel directories).................17 Skip filename specifications, definition.....................................6 Skip filenames, how to specify...............................................7 SORT.EXE required in UpDate module directory for execution of UPDATE N......24 Specify filenames, or specify skip filenames: how to choose.................8 Specify FILENAME[no EXT] with wildcard ".*"..................................9 Suffix-1 (Parallel) directories, definition.................................17 Test "Skip filename specifications" (not done)...............................9 Test "Skip filename specifications" (not done)..............................24 Test PATHS.CNF, possible errors..............................................9 Test the validity of PATHS.CNF...............................................9 Testing of PATHS.CNF, automatic with UPDATE T................................9 Testing of PATHS.CNF, automatic with UPDATE T................................9 TIME function (DOS)..........................................................4 TMP files, automatic deletion or preservation by UpDate......................6 Two hard-drives: copying between............................................20 Universal copy mode: description...........................................14 UpDate installation procedure................................................5 (page 32) UpDate module disk files, list of............................................4 UpDate, comparison with other backup utilities...............................2 UpDate, everyday operation of...............................................11 UpDate, general description..................................................2 UpDate, how it works.........................................................3 UpDate, quick operation checklist...........................................27 UpDate, quick operation checklist...........................................27 UpDate, quick operation checklist...........................................27 UpDate, repeating by backdating LASTDATE.CNF file...........................13 UpDate, run.................................................................11 UpDate, setting the date and time of last back-up procedure.................11 UPDATE N, UpDate newly-added files of old date..............................24 UPDATE T, UpDate path specification test utility.............................9 UPDATE T, UpDate's PATHS.CNF editor..........................................7 Virtual disk copying: procedure............................................21 Mirror-image, Parallel, or <cr> Root dir definition, LASTDATE.CNF...........12 Warning if wrong floppy diskette inserted in drive..........................15 (page 33)